New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename filter param to search api "post_filter" #4119
Comments
I assume I'm using it wrong then:) |
:) It should only be used when you want to aggregate facets on the query results, but then filter out some query results before returning the hits, eg:
If you don't have the faceting requirement, then the color:red filter should be in a filtered query |
I'm not sure where I got the idea that I should just shove whatever filters I'm doing there. Maybe I just inferred it from the parameter name. Maybe some rogue documentation. |
Users tend to use the top-level
filter
param for general filtering, instead of using afiltered
query.It should be renamed to
post_filter
to dissuade users from using it unless they understand what it is for andfilter
should be deprecated.The top level
filter
is still valid field for backwards compatibility, but it will removed in the future.The text was updated successfully, but these errors were encountered: